System and method for an automated validation system

ABSTRACT

System and method are disclosed herein for an automated validation system for validating whether a property of a policyholder receiving at least one insurance benefit is currently receiving remote monitoring services, as claimed by the policyholder. The system comprises an application server, a trusted third party server, and a business logic computer. The application server requests the trusted third party server to validate whether the property of the policyholder is presently receiving remote monitoring services from a service provider. A business logic computer can adjust the policyholder&#39;s insurance policy based on the received validation results.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application 61/365,180 filed on Jul. 16, 2010, the entirety of which is incorporated herein by reference.

FIELD OF INVENTION

In general, the invention relates to the field of validation systems and their use for determining insurance policy adjustments. More specifically, the invention relates to validating whether an insurance company's policyholders who are receiving certain insurance benefits as set forth in their insurance policies because of their use of remote monitoring services in fact are presently receiving such services.

BACKGROUND OF THE INVENTION

Insurance companies generally offer benefits to policyholders whose properties are receiving monitoring services from a remote monitoring service provider based on the reduction in the risk such services provide. These benefits are typically defined in a policyholder's insurance policy, which are adjusted when there are changes to the benefits the policyholder receives. One such benefit is premium discounts, which can be as much as 20% of the non-discounted premium. However, recent underwriting reviews have determined that many policyholders who are receiving such benefits no longer receive remote monitoring services, contrary to the information they had initially provided to the insurance company. This is not surprising given that many policyholders cancel their remote monitoring services after they obtain an insurance policy yet fail to timely inform the insurance company of such a cancellation. However, policyholders without such remote monitoring services should not receive or continue to receive the benefits because the risks associated with their properties are, in fact, not reduced. Conversely, there are policyholders who have recently installed such a monitoring system and should, therefore, be given appropriate benefits.

SUMMARY OF THE INVENTION

Thus, there exists a need for an efficient system that can repeatedly validate whether a policyholder's property is currently being monitored by a remote monitoring services provider so that an insurance company can use such a system to determine an adjustment to the policyholder's insurance policy.

Additionally, because different policyholders may use different types of remote monitoring services covering various aspects of his/her property to differing degrees, there also exists a need for a system that can determine a policyholder's policy adjustment based on the type and scope of coverage of the remote monitoring services the policyholder's property is receiving.

Allowing policyholders to continue to receive benefits after they have canceled their monitoring services reduces the incentive of the policyholders to continue their services with the service provider. At the same time, insurance companies and service providers generally do not want to share data with each other for various reasons, such as to protect the privacy of their policyholders, to protect the value of their customer lists, etc. Therefore, there exists a further need for a secure validation system to allow an insurance company and service providers to validate information provided by their respective customers without sharing each other's data or with a minimum amount of data sharing or exchange.

A system and method are disclosed herein for an automated validation system for repeatedly validating whether a property of a policyholder receiving an insurance benefit is presently receiving remote monitoring services as claimed by the policyholder.

The system comprises an application server in communication with a trusted third party server and a business logic computer. The application server obtains information from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company. A portion of the information indicates that the at least one property of the at least one policyholder is receiving remote monitoring services from a service provider. The application server requests the trusted third party to validate whether the at least one property of the at least one policyholder is currently receiving remote monitoring services from the service provider. The application server stores the validation results in the database. The business logic computer determines an insurance policy adjustment given to the at least one policyholder based, at least in part, on the validation results stored in the database.

In some embodiments, the validation results include information about a type and a scope of coverage of remote monitoring services that the property is receiving. The policy adjustment comprises one of a change insurability of the property, policy premium discount, deductible, and dividend. The system further comprises a communication interface configured to notify the policyholder of the policy adjustment via at least one of mail, email, text messages, a web-based application, and telephone calls. The business logic computer is hosted on a same computer system as the application server. Based at least in part on the validation results, the business logic computer can determine a monetary penalty for the policyholder. The trusted third party server can prevent the insurance company and the service provider from exchanging their respective customer lists. The system further comprises a sensor data collection system configured to receive sensor data associated with the remote monitoring services. The sensor data collection system can communicate with the application server. The application server also communicates with an emergency service provider.

According to one aspect, the method comprises obtaining by an application server from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company, wherein a portion of the information indicates that at least one property of the at least one policyholder is receiving remote monitoring services from a service provider. The method also comprises requesting, by the application server, a trusted third party server to validate whether the policyholder is receiving remote monitoring services from the service provider. The method further comprises storing by the application server in the database validation results received from the trusted third party. The method finally comprises determining by a business logic computer in communication with the application server an insurance policy adjustment given to the policyholder based at least in part on the validation results stored in the database.

According to yet another aspect, the invention relates to a non-transitory computer readable medium storing computer executable instructions, which, when executed by a processor, cause the processor to carry out the method and system functionality described above.

According to a further aspect, the system described above can validate whether a policyholder of an insurance company is receiving remote monitoring services without a trusted third party. The application server can communicate with a service provider server directly to perform the validation without revealing the identity of the policyholder to the service provider. The application server stores validation results in an insurance company's database. In some embodiments, the application server requests from the service provider server a hashed list of customers of the service provider who are receiving remote monitoring services for their properties. The validation results include at least a comparison between the hashed list of customers of the service provider and a hashed list of policyholders of the insurance company presently receiving at least one insurance benefit due to their usage of remote monitoring services for their properties.

BRIEF DESCRIPTION OF THE FIGURES

The methods and systems may be better understood from the following illustrative description with reference to the following drawings in which:

FIG. 1 is a flow chart of a method of determining insurance premium discounts according to an illustrative embodiment of the invention;

FIG. 2 is a diagram of a graphical user interface, in this instance, a web page, suitable for obtaining information relevant to insurance premium discounts, according to an illustrative embodiment of the invention;

FIG. 3 is a peer-to-peer architectural model of an automated validation system, according to an illustrative embodiment of the invention;

FIG. 4 is a client-server architectural model of an automated validation system, according to an illustrative embodiment of the invention;

FIG. 5 is a block diagram of a computer system used in FIGS. 3 and 4, according to an illustrative embodiment of the invention; and

FIG. 6 is a schematic diagram of an insurance scenario, according to an illustrative embodiment of the invention.

DETAILED DESCRIPTION

To provide an overall understanding of the invention, certain illustrative embodiments will now be described, including a system and method for automated repeated validation of information provided by a policyholder for determining insurance discounts. However, it will be understood by one of ordinary skill in the art that the systems and methods described herein may be adapted and modified as is appropriate for the application being addressed and that the systems and methods described herein may be employed in other suitable applications, and that such other additions and modifications will not depart from the scope thereof.

A “property”, as used herein, may be any personal assets, or residential, commercial, or public property and its associated building structures and grounds. Examples of a property include, without limitation, a home and its associated grounds, an apartment complex, a condominium building, an office building, aircrafts, boats, yachts, and ships. A “policyholder”, as used herein, refers to both a potential customer and a current customer of an insurance company.

Insurance companies offer various kinds of insurance benefits to policyholders to encourage them to receive remote monitoring services for their properties. Any change related to the policyholder's use of remote monitoring services may trigger a change in the benefits that the policyholder receives, which may cause the insurance company to adjust the policyholder's insurance policy. To simplify discussions, the following descriptions are largely made in connection with adjusting insurance policies by adjusting policy premium discounts offered to policyholders based on information related to their use of remote monitoring services.

FIG. 1 is a flow chart of a method 100 of determining insurance premium discounts according to an illustrative embodiment of the invention. The method 100 begins with an insurance company determining a base insurance premium for insuring a piece of property (step 102). The insurance company may determine a base premium based on information provided by a policyholder and/or his/her insurance agent. Such information may include public information, prior information, historical information known to the insurance company, and/or information obtained from a third-party about the property and/or the policyholder.

After determining a base premium, the insurance company determines an initial discount for each policyholder (step 104). The discount in one implementation is a fixed discount. In another implementation, the discount is a variable discount determined, for example, to be a fraction of a particular coverage included in the policy, or a fraction of a premium associated with a corresponding peril covered by the policy, etc. Such a determination can be based on information submitted by a policyholder using forms available on a web page (see FIG. 2). Alternatively, or additionally, a policyholder and/or an insurance agent can provide information to an insurance company via other forms of communication, such as, without limitation, telephone calls, postal mail, or in-person communications. Examples of information that may be provided by a policyholder for determining premium discounts are illustrated in FIG. 2 and may include, for example, identification of a central monitoring service or the election of a policy that includes multiple coverages, including, e.g., auto and homeowners and personal umbrella coverage.

Frequently, information which led to a policyholder's initial discount changes. For example, a policyholder who obtained monitoring services when applied for a policy may cancel the services during the term of the policy. Accordingly, the insurance company, on a regular or irregular basis, validates, or verifies, the information that led to the initial discounts. For example, the insurance company may validate the information daily, weekly, bi-monthly, monthly, quarterly, at the end or beginning of every insurance term, randomly, or intermittently. To do so, the insurance company receives validation results about its policyholders' use of remote monitoring services from either a service provider or a trusted third party (step 106). Based on the received validation results, the insurance company determines if a policyholder's initial discount should be adjusted (step 108).

If the received validation results indicate that a policyholder's remote monitoring services status has since changed, the insurance company either reduces or increases the policyholder's initial discounts based on the change or other current information related to the policyholder's remote monitoring services (step 110). A reduction of an initial discount could result in the insurance company withdrawing the discount completely, offering a lesser amount of discount, or imposing a monetary penalty. A policyholder who was previously not offered any discount but is currently receiving monitoring services for his/her property may be awarded a premium discount. Once changes are determined, the insurance company updates data stored in its database to reflect these changes. In some embodiments, once the monitoring services are canceled, the insurance company also lowers a policyholder's coverage limit, as equipment, such as monitoring sensors, associated with the remote monitoring services would no longer be covered, thereby reducing the inventory of goods covered under the policyholder's current policy.

After updating a policyholder's insurance premium or premium discount, the insurance company informs a policyholder of his/her updated premium amount (step 114). The policyholder may be notified via email or via an online account with the insurance company. In other implementations, to ensure the receipt of the notification, the insurance company may notify the policyholder of the change in premium or discount via a postal mail, email or SMS.

If the received validation results confirm the information previously stored in the insurance company's database, a policyholder's initial discount remains unchanged for that validation cycle (step 116). In some embodiments, a policyholder can receive an additional discount for keeping his/her information up to date with the insurance company.

In addition to indicating whether a policyholder is still receiving remote monitoring services, validation results may also include information regarding, for example, the type of remote monitoring services that a policyholder is presently receiving for his/her insured property, which may also change from time to time. Different types of remote monitoring services offer various kinds of security protection; some are of a higher security level than others, and some offer more comprehensive protections than others. In addition, different services also employ different kinds of technology, which offer different levels of safety to the insured properties. For example, some remote monitoring services for protecting against burglary use window alarms for detecting break-ins while other services use laser sensors implemented around the premises of a property. Validation results that the insurance company receives may also include information about the technology used as part of a policyholder's remote monitoring services to allow the insurance company to better determine a policyholder's premium discount such that a policyholder with more advanced remote monitoring services or technology receives a greater discount than policyholders with less advanced remote monitoring services.

In some implementations, as mentioned above, the discount that a policyholder receives may be a variable discount determined to be a fraction of a premium associated with a corresponding peril covered by the policy. Using a home owner's insurance as an example, a policyholder's policy may cover perils such as theft. If a policyholder's property is receiving active anti-theft remote monitoring services for preventing insurance losses associated with theft, the premium discount that the policyholder receives may be a fraction of the portion of the premium that the policyholder is paying for covering the theft peril. Determining a discount based on potential insurance losses that a policyholder's remote monitoring service can prevent encourages the policyholder to continue with the same service, as the benefits of having such a service are now more apparent to the policyholder. Other perils that may be covered under a property insurance policy include, without limitation, fire, lightning, explosion/implosion, aircraft damage, storm, flood, and landslide.

The discount may vary based on other factors, as well. For example, an insurance company may determine a discount for a policyholder based on utilization data related to the policyholder's use of remote monitoring services. Such data may indicate how frequently the policyholder activates the monitoring system, conducts maintenance check-ups on the system, and/or any other information about how such services are being utilized by the policyholder. This way, policyholders who more frequently activate their monitoring systems, for example, receive a greater discount. An insurance company can obtain utilization data directly from a service provider or from a third-party data provider, or by driving from its internal system.

In addition to using information about the property's remote monitoring services for determining a discount, an insurance company may also vary a policyholder's discount based on information about the neighborhood in which a policyholder's property is located. Such neighborhood information may include, for example, the neighborhood's crime rate, average income of all the households in the neighborhood, average property value, and demographics of people residing in the neighborhood. Doing so allows the insurance company to more fairly assess potential insurance risks associated with a policyholder's property, which in turn, allows the insurance company to more fairly determine a policy premium, or premium discount, for the policyholder. For example, a high-crime neighborhood tends to have higher risks of burglary in comparison to a low-crime neighborhood. Therefore, for high-crime neighborhoods, receipt of remote monitoring services may provide a greater benefit than receipt of such services in low-crime neighborhoods. To encourage the use of remote monitoring services in a high-crime neighborhood, policyholders living in a high-crime neighborhood with remote monitoring services may receive a greater premium discount than policyholders in a low-crime neighborhood. In addition, the discount may vary based on the number or percentage of properties in a neighborhood receiving monitoring services. A property located in a neighborhood with a greater usage of remote monitoring services receives a greater discount as this neighborhood characteristic further deters theft in the neighborhood. It also has the added benefit of encouraging further use of such services in the neighborhood, improving all residents' safety.

In some embodiments, an insurance company provides policyholders belonging to the same neighborhood, apartments building, condominiums building, or office building with information related to the use of remote monitoring services in their neighborhood. For example, policyholders may receive information about the total number of households or companies belonging to their neighborhood which are receiving remote monitoring services for their properties. The policyholders can receive such information via email, mail, or text messages. The insurance company can also provide a social media website where information about each neighborhood may be posted and shared among policyholders living in the neighborhood. Each policyholder of a neighborhood can, for example, log onto his/her neighborhood's web page on the social media website to view real-time information about the use of remote monitoring services of others living in the same neighborhood. In some embodiments, policyholders of different neighborhoods may also share their information on the social media website. Offering such a social media website allows policyholders to encourage one another to use remote monitoring services as doing so improves the overall safety of their neighborhood, benefiting everyone in the neighborhood. To protect policyholders' privacy and identities, particularly those without remote monitoring services, identifying information about each policyholder is not revealed such that members, or policyholders, of the social media website can only communicate with one another virtually unless the members choose to reveal their identifying information.

Though the foregoing discussions are made in relation to offering insurance premium discounts to policyholders whose properties are receiving remote monitoring services, an insurance company may offer other kinds of insurance benefits in addition to or in replacement of a premium discount. For example, in some instances, the insurance company may offer to pay for or reimburse a portion of the cost associated with receiving a remote monitoring service and any equipment or systems needed for the service. As another example, the insurance company may lower a policyholder's deductible, e.g., from 2% to 1.5%, or issue credits, e.g., $100, to a policyholder's account with the insurance company that the policyholder may use to pay for insurance-related expenses in the future. The details of an illustrative suitable system and method for administering such payments are further described in co-pending U.S. patent application Ser. No. 12/254,215, the entirety of which is incorporated herein by reference.

If policyholders offered with such alternative forms of incentives cancel their remote monitoring services, the insurance company withdraws its previous offer and/or impose an additional monetary penalty. For example, the insurance company may request the policyholder to repay the cost that the insurance company had paid initially for covering costs associated with purchasing remote monitoring services and the associated equipment.

FIG. 2 is a diagram of a graphical user interface, in this instance, a web page 200, suitable for obtaining information relevant to insurance premium discounts, according to an illustrative embodiment of the invention. The web page 200 includes a series of questions, the answers to which may be used by a business logic computer for determining a policyholder's initial discounts at step 104. Each policyholder may receive a web account with which he/she can provide relevant information used for determining insurance premium discounts by the insurance company. In the case where a policyholder has selected “Yes” to the question “is your property currently receiving remote monitoring services” on the web page 200, the policyholder may be prompted to respond to a list of additional questions specific to the monitoring services. If the policyholder has selected “No” to the question, the insurance company may inform the policyholder that discounts can be received if the property receives remote monitoring services, thereby encouraging the policyholder to obtain remote monitoring services for his/her property. The insurance company may further indicate on the web page 200 an estimate of discounts. The insurance company may also provide to the policyholder a list of preferred remote monitoring service providers and their contact information. The policyholder may then contact the providers directly or be routed to a preferred provider's website from the web page 200.

After selecting “Yes” to the question asking whether monitoring service is being provided, the policyholder may be asked to identify which of the listed service providers is providing the remote monitoring services to the policyholder's property. If “Other” has been selected, the policyholder may be given the option to provide the name of the service provider. The insurance company may also request permission to obtain information from the service provider regarding the type and status of the monitoring service the policyholder's property has. If the user grants the request, the insurance company periodically or intermittently, through an automated validation system, verifies whether the insured property is presently receiving the remote monitoring services or any other information pertinent to the determination of premium discounts. For example, the insurance company can also periodically or intermittently verify whether the type of monitoring services that the insured property is receiving has changed since the last validation cycle. This way, policyholders no longer need to update the information on file with the insurance company if it changes, because the stored information is updated automatically by the insurance company.

The insurance company may further ask the policyholder to grant it access to monitoring data. Monitoring data may be data collected by various sensors currently implemented as part of the remote monitoring system for detecting a variety of conditions of the property, including, without limitation, fire hazards, carbon monoxide levels, water leakage, break-ins, low temperatures, etc. Having real-time data transmitted to the insurance company enables the insurance company to proactively detect, or identify a potential cause of loss and quickly eliminate the cause to prevent any damages from occurring, or mitigate a loss after it has occurred. Emergency service providers (e.g., fire departments, hospitals, policy stations, plumbing companies, electricians, etc.) may be contacted directly after a potential cause of loss is detected. For example, the real-time sensor data can indicate that pressure exerted on a water pipe has exceeded a threshold value and a potential rupture of the pipe may occur. As another example, the sensor data can indicate that a gas stove was left on and is currently emitting carbon monoxide. Having access to the monitoring data can also assist the insurance company in determining and processing damage claims without having to involve the policyholder to contact the insurance company for on-site damage assessment. Other benefits and methods for having access to monitored data are described in U.S. Pat. Nos. 7,610,210 and 7,711,584, the entirety of which are herein incorporated by reference.

Using the web page 200, the insurance company may also ask the policyholder to select the type of sensor used in the remote monitoring system. For example, the service elected by the policyholder may include a water leakage sensor for detecting water leakage. Selection of one sensor is not mutually exclusive of the selection of another. Many remote monitoring systems come with a variety of sensors installed on the premises of a property for monitoring various aspects of the property. Such detailed information may be used by the insurance company's business logic computer to determine additional discounts that the policyholder may qualify for (step 106). For example, a policyholder with both a burglary detector and a water leakage sensor may receive a greater insurance discount than a policyholder with only a burglary detector, since the risks are lower for a property receiving more comprehensive monitoring services. However, if the policyholder does not know what type of sensor is used as part of the monitoring system, the insurance company may, after receiving the policyholder's consent, request such sensor data be sent from a sensor data collection center, either directly or indirectly via a trusted third party.

The insurance company may also ask the policyholder if the policyholder wishes to use preferred emergency service providers to prevent or mitigate a loss when a repair or other preventive or remedial services are needed (e.g., to put out a fire, to eliminate a source of carbon monoxide, to relieve water pressure in a pipe before rupture, or to remove standing water from a basement). A preferred service provider that is not a public entity, e.g. a fire department, may also be referred to as an in-network service provider in an insurance company's private network. By selecting such an in-network or preferred emergency service provider, a policyholder may receive a greater discount as a result than a policyholder who chose to use an out-of-network service provider. Preferred emergency service providers may be contacted directly after detecting that a potential loss might occur or after an incident is detected. This way, potential hazards or losses may be eliminated before they mature into actual incidents. If an incident is not averted, the service provider, by being timely notified of the incident, may be able to mitigate the potential losses associated with the incident. Once an incident does occur, the policyholder may also avoid any hassles associated with finding emergency service providers covered under an elected insurance policy. Since preferred emergency service providers have established business relationships with the insurance company and/or the remote monitoring service providers, bills incurred by any emergency service provider may automatically be sent to the insurance company, instead of the policyholder, who typically has to file claims him/herself.

It should be noted that the questions listed on web page 200 may be filled out by a policyholder or the policyholder's insurance agent. Additionally, the listed questions are used only as examples of information that may be relevant to an insurance company for determining insurance premium discounts that a policyholder is eligible for. Since an insurance company needs to validate information about its policyholders against information that a service provider may have about these policyholders if they are also customers of the service provider, questions depicted on web page 200 may include or be made based on questions that a remote monitoring service provider generally gives to its customers.

In some embodiments, questions depicted on web page 200 are delivered to policyholders via mail, posed over the phone, or disseminated via another mode of communication. A policyholder can also return his/her answers to these questions via mail, orally, or otherwise. Insurance personnel can update an insurance company's electronic database by storing the answers.

FIG. 3 is a peer-to-peer architectural model of an automated validation system 300, according to an illustrative embodiment of the invention. The validation system 300 includes an insurance company's validation platform 304, which supports an application 306. The validation platform 304 may support additional applications provided by other entities. The application 306 may also include a web application to support the web page 200. The validation platform 304 and application 306 can communicate with the insurance company's database 302 using a peer-to-peer communication protocol. The database 302, validation platform 304 and application 306 may be part of a computer system 500, a description of which is provided below with respect to FIG. 5. Alternatively, or in addition, these components may be located separately in different computer systems. The validation platform 304 and application 306 are connected to a trusted third party 310, also using a peer-to-peer communication protocol. The trusted third party 310 may be a computer system, such as a server, run by a third party company for processing data received between two relying parties, such as the insurance company and one or more service providers. The trusted third party 310 is connected to service provider 314 and service provider 318, also using a peer-to-peer communication protocol. Service provider 314 and service provider 318 are also connected to a database 316 and 320 respectively. The automated validation system 300 may be based on Secure Multiparty Computation/Communication (Secure MPC) to protect the privacy and anonymity of the insurance company's policyholders as well as that of the customers of the service providers 314 and 318. Alternatively, or in addition, the insurance company's validation platform 304 may communicate directly with the service providers 314 and 318 without communicating through the trusted third party.

Validation platform 304 may utilize or combine any one of well-known software development platforms, open or closed, such as Microsoft .NET, Java, Adobe AIR, Steam, etc. Operating system platforms for supporting the validation platform 304 may include: Microsoft Windows, Unix, MAC OS, Solaris, IBM DB2, or any virtual machine operating system platforms. The platforms, applications, and operating systems may run on a computer system 500, a server, or the like. The validation platform 304 may include an Application Programming Interface, API, which would allow easy plug-ins of other entities' applications to communicate with application 306. Databases 302, 316, and 320 may be any well-known memory or storage elements capable of retaining or storing electronic data. Databases 302, 316, and 320 may also include database applications, drivers, middleware, firmware, and/or operating systems to allow the retrieval and storing of data.

In operation, the application 306 may first query the database 302 for a list of policyholders who are currently receiving property insurance premium discounts. The application 306 may then filter the list to identify policyholders who are receiving discounts because their properties are receiving remote monitoring services. The application 306 may further identify the names of the service providers for the list of policyholders currently receiving insurance discounts, which may be based on information previously submitted to the database 302 via web page 200. Once the names of the service providers are identified, the application 306 provides the names of the service providers to the trusted third party 310 who establishes communication with the computer systems of the identified service providers. To protect policyholders' privacy and their data security, the establishment of communication may follow protocols typically associated with a secure MPC system in which data to be transmitted and received are routed through a trusted third party 310. A trusted third party 310 may compare the name of a policyholder against names of all the service providers' customers to determine if a match has been found. Once a match has been identified, the trusted third party 310 may obtain additional data about that policyholder from the service provider and create validation results to reflect such a match and/or any other relevant information. By having the trusted party compare data received from the insurance company and the service providers, the insurance company can avoid revealing the identities and sensitive information of its policyholders to other entities, as might be required by contract, law, or other constraints, while still allowing the insurance company to validate its stored information about its policyholders. Similarly, service providers also benefit from such a trusted system as their customers' data is also protected and not shared with other parties or entities.

For policyholders who have been identified in the service providers' database 316 or 320, the trusted third party 310 requests from the service providers their services status to determine whether they are presently receiving remote monitoring services. In an alternative embodiment, the service providers deliver their customers' current service status along with the initial customer list directly to the trusted third party 310. Once the trusted third party 310 determines that the policyholders are indeed receiving the remote monitoring services, validation results may be sent back to the application 306 which may, in turn, provide the results back to the business logic computer of the insurance company for further processing.

If the trusted third party 310 determines that some of the insurance company's policyholders do not match any customers' names in the service providers' databases, the trusted third party 310 may first approximate the names of the policyholders to be within a predefined code distance apart from the original names to determine alternate names that may be stored in the service providers' databases. The trusted third party 310 may also store in its system a phonetic algorithm, such as Soundex, used for indexing names by sound, as pounced in English, so that different versions of a name may be standardized or normalized. Other information that can aid in this process may include the policyholder's permanent mailing address, telephone number, or spousal name, if any, and/or social security number etc. After the approximation analysis, if the trusted third party 310 is still unable to identify the policyholders in the service providers' databases, the trusted third party 310 may flag the policyholders as not receiving remote services and send the results back to the application 306.

In some embodiments, for a policyholder whose name does not match any customers of the service providers, as verified by the trusted third party 310, the insurance company can request these policyholders to i) verify information stored in the database 302 to correct any errors in their names and/or street addresses stored in the database 302, 316, and/or 330, and/or ii) provide proof of remote monitoring services, such as bills received from the service provider. This way, the insurance company can avoid mistakenly withdrawing premium discounts offered to these policyholders due to a computational error. If a policyholder has different information stored in the database 302, (e.g. the last name has since changed), the insurance company may send the updated data to the trusted third party 310 for re-validation.

In some instances, some of the policyholders no longer receive the remote monitoring services from the service providers 314 or 318. Accordingly, the service providers 314 and 318 may provide data indicating termination of service of these policyholders to the trusted third party. Before sending such data, the service providers 314 and 318 may first determine the nature of the terminated service. In some cases, the policyholders' services may have been terminated because payment for the services was past due for a predefined amount of time. In those cases, data sent by the service providers 314 and 318 may reflect such information so that the insurance company may, instead of withdrawing discounts from the insurance premiums, remind the policyholders that the remote monitoring services need to be reactivated for them to continue to receive the insurance discounts. It should be noted that there are other scenarios in which an unintentional temporary lapse of service can occur and those scenarios should be handled differently from an intentional cancellation.

In instances where the cancellation of remote monitoring services was intentional, the service providers 314 and 318 may provide data that would reflect such an intentional cancellation to trusted third party 310. The trusted third party 310 may then embed such information in the validation results of that policyholder to the insurance company's application 306. The application 306 may send data to the business logic computer for adjusting the insurance discounts accordingly. In some embodiments, the application 306 can generate automatic notifications to the policyholders indicating that termination of monitoring services will cause the withdrawal of premium discounts. The policyholders may be given a predefined period of time to renew the monitoring services in order to continue benefiting from the discounts. Alternatively, the policyholder may be given the option to provide proof of receiving the monitoring services in case such determination of terminated service was incorrect or the policyholder has since changed service provider. In other embodiments, the insurance company can simply withdraw the discounts when the validation results reflect the termination of services.

In some scenarios, the service providers can provide the insurance company, via the trusted third party 310, with the date of termination of the monitoring services for a given policyholder. Thus, the application 306 may further calculate discounts that were given to the policyholder when they were not in fact eligible. The insurance company 306 can then retroactively bill the policyholders for the discounts that were incorrectly given to them. In other instances, the insurance company can also be given the information indicating hat the policyholders have either upgraded or downgraded the monitoring services. For example, for the policyholders who have previously submitted through the forms on web page 200 that the insured property is receiving anti-burglary, water leakage, and fire detection monitoring services, but has since changed the monitoring services to cover only anti-burglary, the insurance company can revoke some portions of the initial discount, since the risks associated with the insured property have increased due to the downgrade of monitoring services. As another example, some policyholders may have upgraded their services to include both anti-burglary and carbon monoxide detection as opposed to only anti-burglary; the insurance company will, upon receiving such information by the application 306, credit the policyholders additional discounts for lowering their property's insurance risks.

After validating the stored information about policyholders who have been receiving property discounts, the application 306 may then generate a list of remaining policyholders who are not currently receiving the discounts. The insurance company may then send the list to the trusted third party 310 to identify policyholders who are eligible for discounts but have not provided relevant information that would trigger the discounts. In other words, to ensure that qualified policyholders are receiving their eligible discounts, the application 306 may query the database 302 for a list of policyholders without discounts. The trusted third party 310 may perform the same analysis as mentioned before and return validation results to the application 306. If the identified policyholders without discounts do not exist in the service providers' databases 316 and 320, the insurance company may keep the insurance premium at the same level. In some implementations, the application 306 can remind the policyholder that receiving monitoring services for his or her property will qualify him/her for premium discounts. If the identified policyholders without discounts are customers of the service providers, the business logic computer may update and apply the insurance premiums accordingly. Finally, the application 306 may generate an automatic notice, delivered via email or postal mail, to the policyholder informing him or her of the discounts. Accordingly, names and information of policyholders who are now identified as having the monitoring services may be indexed and stored among other policyholders who are currently receiving discounts associated with property monitoring services.

It should be noted that additional trusted third parties or service providers may be included in the validation system 300. As a simple illustration, only two service providers and one trusted third party are illustrated in FIG. 3. The API of the validation platform 304 may allow easy plug-ins of additional service providers' applications for communicating with the application 306. Alternatively, the insurance company, service providers, and trusted third party may identify an agreed-upon protocol for communicating among themselves, without using an API. The validation system 300 may also be configured in such a way to avoid future validation requests from the insurance's application 306. That is, once a list of policyholders has been provided to the trusted third party 310, no repeated requests for validation of these policyholders are needed from the insurance company. In fact, only changes in the list of policyholders may be sent to the trusted third party 310 (e.g., new policyholders, etc.). Similarly, the trusted third party 310 may receive only changes in the customer list and/or account status of existing customers of the service providers.

In alternative implementations, application 306 and service providers 314 and 318 may communicate with each other directly, without using a trusted third party 310. In these implementations, the data comparison and validation may be done by either a computer system of the insurance company or the service providers in such a way that information, or data, about their respective customers is not shared among themselves in a fashion that would disclose private or proprietary information as described further below.

FIG. 4 is a client-server architectural model of an automated validation system 400, according to an illustrative embodiment of the invention. The automated validation system 400 includes a validation platform 302, which hosts an application 306. Both the validation platform 304 and application 306 may be connected to a database 302 through a local area network directly or through internet 402. The validation system 400 also includes a trusted third party 310 and service providers 314 and 316. The service providers 314 and 318 are connected to databases 316 and 320 respectively. Service provider systems 314 and 318 may link to databases 316 and 320 through a local area network or the internet 402. The validation system 400 also includes an insurance company 408 for hosting one or more applications related to determining insurance premiums, such as the business logic application or system. Each component of the validation system 400 may also communicate with one another, directly or indirectly, through the internet 402. In some implementations, where the validation system 400 conforms to the standards and protocols of a Secure MPC system, the application 306 of the validation platform 304 communicates with the service providers 314 and 318 respectively via the trusted third party 310. The trusted third party 310 compares data received from both the insurance company and the service providers. The trusted third party 310 creates the validation results based on the comparison data and sends the results to the insurance application 306. Various software and/or system level software and hardware components that are suitable for the validation platform 304 are described above with respect to FIG. 3. The databases 302, 316, and 320 may be hosted by the same physical storage elements, portions of which may be partitioned to allow the access of the application 306 and/or the service providers 314 and 316. A detailed hardware description and examples of a database are provided in the description of FIG. 5.

As described with respect to FIG. 3, application 306 of the insurance company may request the trusted third party 310 to validate information stored in its database 302. In particular, the application 306 may allow the insurance company to communicate with the trusted third party to validate whether its insured properties are receiving monitoring services as claimed by its policyholders. The application 306 may query the insurance company's database 302 for a list of policyholders who are benefiting from the discounts and may then identify names of the service providers for providing the monitoring services to the policyholders' properties. The identified service providers who have applications hosted on the validation platform 304 may return their customers' data to the trusted third party 310, which computes and returns the validation results to the insurance company. The validation results may be received by the application 306 and processed by the business logic computer located either on the validation platform 304 or at the insurance company 408. If the business logic computer is located remotely at the insurance company 408, the application 306 may communicate with the business logic computer via the internet. Depending on the validation results, the insurance premium discounts may then be determined according to the method described with respect to FIG. 1.

In some implementations, instead of communicating with the service providers 314 and 318 via the trusted third party 310, the application 306 may communicate directly with the service providers 314 and 318. To protect the anonymity of the insurance company's policyholders, the insurance company may hash the names of the policyholders whose account status of the remote monitoring service is to be determined by the service providers 314 and 318. Alternatively, or additionally, the insurance company may also hash other identifying information about its policyholders, such as their permanent mailing addresses, social security card numbers, telephone numbers, and/or spousal names, if any. The validation platform may support shared one-way hash functions, such as SHA-512, to allow both the application 306 and service providers 314 and 318 to hash their customers name and/or street addresses using the same hash function. For example, the application 306 may use a one-way hash function to hash all the names of policyholders whose account status is to be validated. The application 306 may send the hash values associated with each policyholder and information about which hash function was used to the service providers 314 and 318. The service providers 314 and 318 may then hash their customers using the same hash function and return their hash values to the application 306 for comparison. To combat dictionary attack or other common attacks associated with one-way hash functions, the insurance company may further store a list of salt (strings used to randomize and increase the length of data to be hashed) to be concatenated with the names, or other identifying information, of the policyholders to randomize the value to be hashed. The salt could be, for example, binary strings (e.g., ASCII codes) for “Yes” and/or “No”. Alternatively, the insurance company may use information about the type of remote monitoring services that a policyholder has elected for his/her property as the salt. This way, the insurance company can verify whether the policyholders exist in the database of a service provider without exposing the names or detailed information about its policyholders to the service provider. This can also prevent hackers from intercepting their stored data.

In other implementations, policyholders who are also customers of service providers 314 and 318 may directly validate the account status in accordance with the open standard OAuth, which allows users to grant a third party site access to their information stored in another party's website, such as a service provider's website. Such authorization protocols or standards have been generally used in the field of social media. However, similar concepts can supplement or replace the existing secure MPC models in which information received from two relying parties are being accessed and processed by a trusted third party. To use OAuth, policyholders of the insurance company would need to establish an online account with both the insurance company and with the service providers. A policyholder may first log into his/her account with the insurance company. Subsequently, the policyholder may log into his/her account with the service provider 314. The insurance company can receive a token from the service providers' website after the policyholder has successfully logged into the service provider's website. The token may indicate to the insurance company that the policyholder indeed is an active customer of the service provider. Once a communication session is established after the policyholder has logged onto both accounts, other information stored in the service provider's databases 316 and 320 may be shared with the insurance company's application 306, without providing the insurance company direct access to the policyholder's account with the service providers, and vice versa.

FIG. 5 is a block diagram of a computer system 500 used in FIGS. 3 and 4 for supporting various software applications or application platforms such as the validation platform 304, according to an illustrative embodiment of the invention. Computer system 500 comprises at least one central processing unit (CPU) 502, system memory 508, which includes at least one random access memory (RAM) 510 and at least one read-only memory (ROM) 512, at least one network interface unit 504, an input/output controller 506, and one or more data storage devices 514. All of these latter elements are in communication with the CPU 502 to facilitate the operation of the computer system 500. The computer system 500 may be configured in many different ways. For example, computer system 500 may be a conventional standalone computer or alternatively, the function of computer system 500 may be distributed across multiple computer systems and architectures. In the embodiment shown in FIG. 4, the computer system 500 is linked, via network 402 (also described in FIG. 4), to an insurance company computer system 408 which may house a portion of the business logic that may be called by the application 306 for determining insurance premium discounts.

Computer system 500 may be configured in a distributed architecture, wherein databases and processors are housed in separate units or locations. The computer system 500 may also be seen as a server located either on site near the insurance company 408, or can be accessed remotely by the insurance company 408. Some such units perform primary processing functions and contain at a minimum, a general controller or a processor 502 and a system memory 508. In such an embodiment, each of these units is attached via the network interface unit 504 to a communications hub or port (not shown) that serves as a primary communication link with other servers, client or user computers and other related devices. The communications hub or port may have minimal processing capability itself, serving primarily as a communications router. A variety of communications protocols may be part of the system, including, but not limited to: Ethernet, SAP, SAS™, ATP, BLUETOOTH™, GSM and TCP/IP.

The CPU 502 comprises a processor, such as one or more conventional microprocessors and one or more supplementary co-processors such as math co-processors for offloading workload from the CPU 502. The CPU 502 is in communication with the network interface unit 504 and the input/output controller 506, through which the CPU 502 communicates with other devices such as other servers, user terminals, or devices. The network interface unit 504 and/or the input/output controller 506 may include multiple communication channels for simultaneous communication with, for example, other processors, servers or client terminals. Devices in communication with each other need not be continually transmitting to each other. On the contrary, such devices need only to transmit to each other as necessary, may actually refrain from exchanging data most of the time, and may require several steps to be performed to establish a communication link between the devices.

The CPU 502 is also in communication with the data storage device 514. The data storage device 514 may comprise an appropriate combination of magnetic, optical and/or semiconductor memory, and may include, for example, RAM, ROM, flash drive, and/or an optical disc such as a compact disc and/or a hard disk or drive. The CPU 502 and the data storage device 514 each may be, for example, located entirely within a single computer or other computing device, or connected to each other by a communication medium, such as a USB port, serial port cable, a coaxial cable, an Ethernet type cable, a telephone line, a radio frequency transceiver or other similar wireless or wired medium or combination of the foregoing. For example, the CPU 502 may be connected to the data storage device 514 via the network interface unit 504.

The data storage device 514 may store, for example, (i) an operating system 516 for the computer system 500; (ii) one or more applications 518 (e.g., computer program code and/or a computer program product) adapted to direct the CPU 502 in accordance with the present invention, and particularly in accordance with the processes described in detail with regard to the CPU 502; and/or (iii) database(s) 520 adapted to store information that may be utilized to store information required by the program. In some embodiments, the database(s) 520 store(s) policyholder information such as information relevant to determining the insurance premium discounts, base premium, property insurance compliance guidelines for one or more jurisdictions, policyholder policy provisions for one or more different types of insurance policies, claims information, and/or prior records of the policyholder's property and the like.

The operating system 516 and/or applications 518 may be stored, for example, in a compressed, uncompiled and/or encrypted format, and may include computer program code. The instructions of the program may be read into a main memory of the processor from a computer-readable medium other than the data storage device 514, such as from the ROM 512 or from the RAM 510. While execution of sequences of instructions in the program causes the processor 502 to perform the process steps described herein, hard-wired circuitry may be used in place of, or in combination with, software instructions for implementation of the processes of the present invention. Thus, embodiments of the present invention are not limited to any specific combination of hardware and software.

Suitable computer program code may be provided for performing numerous functions such as determining insurance premium discounts of policyholders based on validation results associated with their remote monitoring services. The program also may include program elements such as an operating system, a database management system and “device drivers” that allow the processor to interface with computer peripheral devices (e.g., a video display, a keyboard, a computer mouse, etc.) via the input/output controller 506.

The term “computer-readable medium” as used herein refers to any non-transient medium that provides or participates in providing instructions to the processor of the computing device (or any other processor of a device described herein) for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical, magnetic, or opto-magnetic disks, such as memory. Volatile media includes dynamic random access memory (DRAM), which typically constitutes the main memory. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM or EEPROM (electronically erasable programmable read-only memory), a FLASH-EEPROM, any other memory chip or cartridge, or any other medium from which a computer can read.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to the processor 502 (or any other processor of a device described herein) for execution. For example, the instructions may initially be borne on a magnetic disk of a remote computer (not shown). The remote computer can load the instructions into its dynamic memory and send the instructions over an Ethernet connection, cable line, or even telephone line using a modem. A communications device local to a computing device (e.g., a server) can receive the data on the respective communications line and place the data on a system bus for the processor. The system bus carries the data to main memory, from which the processor retrieves and executes the instructions. The instructions received by main memory may optionally be stored in memory either before or after execution by the processor. In addition, instructions may be received via a communication port as electrical, electromagnetic or optical signals, which are exemplary forms of wireless communications or data streams that carry various types of information.

FIG. 6 is a schematic diagram of an insurance scenario 600, according to an illustrative embodiment of the invention. The insurance scenario 600 comprises a network of properties, which includes a home 602, 604, and 606, an apartment building 610, a condominium building 612, and an office building 614. The scenario 600 also includes a sensor data collection center 620, an insurance company 622, and emergency service providers 624 and 626. Homes 602, 604, and 606 are owned by separate families. The apartment building 610, condominium building 612, and office building 614 are owned by a group of individuals or families, each of whom may be a policyholder of the insurance company 622. In some instances, the buildings 610, 612, and 614 are managed by a centralized management company which insures the entire building, in addition to the insurance purchased by the each unit's owner. The scenario 600 also includes a sensor data collection office 620 for receiving sensor data generated by various sensors implemented on or near the premises of monitored properties. The collection office 620 may be owned by a remote monitoring service provider. Alternatively, or in addition, the collection office 620 may be co-owned by both a service provider and the insurance company 622. The emergency service providers 624 and 626 include companies, government entities (e.g., police station, fire station), hospitals, or individuals offering emergency services, such as fixing water leakage. The emergency service providers 624 and 626 may be preferred providers of the insurance company 622. These providers may have electronic equipment or notification systems connected to a computer system of insurance company 622 and/or the collection center 620 for receiving real-time notification in case a policyholder is in need of their services. Similarly, the insurance company 622 may be connected directly or indirectly to the collection center 620 for receiving and processing data received in real-time.

In the scenario 600, home 602 may be an insured property currently receiving property insurance discounts, because it is receiving remote monitoring services for detecting burglary. Similarly, the home 604 is another insured property, but is not currently receiving any remote monitoring services. The home 606 may be another insured property insured by the insurance company 622. The remote monitoring services for the home 606 may include: fire detection, carbon monoxide level detection, water leakage detection, and burglary detection. Since each home is receiving different monitoring coverage, each policyholder may be offered a different insurance policy and premium. For example, the insurance premium for the owner of the home 602 is $65/month, while the premium for the owner of the home 604 is $80/month, the full amount, and owner of the home 606 is only paying $50/month, because the home 606 has the most comprehensive monitoring coverage. For homes 602 and 606, various sensors may be installed in and around the homes and data collected using the sensors may be sent to the collection center 620 automatically. It should be noted that types of sensors used for remote monitoring are well known in the art. These sensors may detect, encode and transmit data using various electromagnetic or acoustic waves, such as, without limitation, radio waves, microwaves, infrared, ultrasonic waves, and the like. Sensors may repeatedly, intermittently, or continuously send the monitoring data to the collection center 620 over the internet or wired connections. Alternatively, the data may be sent only if an abnormality is detected.

In the scenario 600, the collection center 620 may also collect real time data about the various aspects of the insured properties so that the insurance company 622 may use such data to determine damages, in addition to verifying whether the policyholders are receiving the monitoring services. For example, the collection center may receive sensor data such as the pressure of the water in the pipe before the pipe burst, humidity surrounding the pipe, the amount of water that has leaked as a result, and/or the like. The received data may also be used by the insurance company 622 to determine which emergency service provider to contact for preventing causes of loss, mitigating a loss, or repair any resulting damage from a loss. Since the emergency service providers 626 may be connected directly to the sensor data collection center 620, the providers may be contacted in real time. Having such sensor data may also assist the emergency service provider in assessing the conditions and situation to more easily identify ways to eliminate a cause of loss or to repair damages.

In buildings such as the apartment building 610, condominium building 612, or the office building 614, sensors may be installed in each individual unit or office within the buildings. A central data collector may also be installed inside the apartment building for collecting data received from each unit or office. Centralized data collectors may be implemented on a per floor basis. There may also be servers that manage all the received data for an entire building. Such servers may also house other information used by an on-site management office for transmitting received data from each unit to the collection center 620. The server may further be connected to a database for indexing data collected for each unit currently receiving monitoring services. One or more units may use a different service provider for their monitoring services. Therefore, each unit may also be indexed to include information about the type of monitoring services as well as the name of the service provider. Finally, each sensor implemented in a unit may communicate with the collection center wirelessly or through wired connections.

The invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The foregoing embodiments are therefore to be considered in all respects illustrative, rather than limiting of the invention. 

1. An automated validation system for validating information used to determine insurance policy adjustments, comprising: an application server for: obtaining from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company, wherein a portion of the information indicates that at least one property of the at least one policyholder is receiving remote monitoring services from a service provider; requesting a trusted third party server to validate whether the at least one property of the at least one policyholder is currently receiving remote monitoring services from the service provider; and storing in the database validation results received from the trusted third party server, and a business logic computer in communication with the application server for determining an insurance policy adjustment given to the at least one policyholder based at least in part on the validation results stored in the database.
 2. The system of claim 1, wherein the insurance policy adjustment comprises one of a change in insurability of the at least one property, policy premium discount, coverage limit, deductible, and dividend.
 3. The system of claim 1, wherein the validation results include information about a type and a scope of coverage of remote monitoring services the property is receiving.
 4. The system of claim 1 further comprising a communication interface configured to notify the at least one policyholder of the policy adjustment via at least one of mail, email, text messages, a web-based application, and telephone calls.
 5. The system of claim 1, wherein a portion of the business logic computer is hosted on a same computer system as the application server.
 6. The system of claim 1, further comprising a sensor data collection system configured to receive sensor data associated with the remote monitoring services, wherein the collection system is in communication with the application server.
 7. The system of claim 1, wherein the application server is in communication with an emergency service provider.
 8. The system of claim 1, wherein the application server requests the trusted third party to repeatedly validate the information about the at least one policyholder.
 9. The system of claim 1, wherein the business logic computer is configured to determine a monetary penalty for the at least one policyholder based at least in part on the validation results.
 10. The system of claim 1, wherein the trusted third party server is configured to prevent the insurance company and the service provider from exchanging their respective customer lists.
 11. A non-transitory computer readable medium storing computer executable instructions, which, when executed by a processor, cause the processor to carry out a method comprising: obtaining from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company, wherein a portion of the information indicates that the at least one property of the at least one policyholder is receiving remote monitoring services from a service provider; requesting a trusted third party server to validate whether the at least one property of the at least one policyholder is currently receiving remote monitoring services from the service provider; storing validation results received from the trusted third party server; and determining an insurance policy adjustment given to the at least one policyholder based at least in part on the validation results stored in the database.
 12. The non-transitory computer readable medium of claim 11, wherein the insurance policy adjustment comprises one of a change in insurability of the at least one property, policy premium discount, coverage limit, deductible, and dividend.
 13. The non-transitory computer readable medium of claim 11, wherein the validation results include information about a type and a scope of coverage of remote monitoring services the property is receiving.
 14. The non-transitory computer readable medium of claim 11, wherein the method further comprises notifying the at least one policyholder of the policy adjustment via at least one of mail, email, text messages, a web-based application, and telephone calls.
 15. The non-transitory computer readable medium of claim 11, wherein the method further comprising receiving sensor data from a sensor data collection system associated with the remote monitoring services, wherein the sensor data collection system is in communication with the application server.
 16. The non-transitory computer readable medium of claim 11, wherein the method further comprising determining a monetary penalty for the at least one policyholder based at least in part on the validation results.
 17. The non-transitory computer readable medium of claim 11, wherein the method further comprising requesting the trusted third party to repeatedly validate the information about the at least one policyholder.
 18. The non-transitory computer readable medium of claim 11, wherein the method further comprising preventing the insurance company and the service provider from exchanging their respective customer lists.
 19. A method for validating information used to determine insurance policy adjustments, comprising: obtaining by an application server from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company, wherein a portion of the information indicates that at least one property of the at least one policyholder is receiving remote monitoring services from a service provider; requesting by the application server a trusted third party server to validate whether the at least one property of the at least one policyholder is currently receiving remote monitoring services from the service provider; storing by the application server in the database validation results received from the trusted third party server; and determining by a business logic computer in communication with the application server an insurance policy adjustment given to the at least one policyholder based at least in part on the validation results stored in the database.
 20. The method of claim 19, wherein the insurance policy adjustment comprises one of a change in insurability of the at least one property, policy premium discount, coverage limit, deductible, and dividend.
 21. The method of claim 19, wherein the validation results include information about a type and a scope of coverage of remote monitoring services the property is receiving.
 22. The method of claim 19, further comprising notifying, by a communication interface, the at least one policyholder of the policy adjustment via at least one of mail, email, text messages, a web-based application, and telephone calls.
 23. The method of claim 19, further comprising hosting a portion of the business logic computer on a same computer system as the application server.
 24. The method of claim 19, further comprising receiving by a sensor data collection system sensor data associated with the remote monitoring services, wherein the collection system is in communication with the application server.
 25. The method of claim 19, further comprising establishing communication between the application server and an emergency service provider.
 26. The method of claim 19, further comprising requesting, by the application server, the trusted third party to repeatedly validate the information about the at least one policyholder.
 27. The method of claim 19, further comprising determining by the business logic computer a monetary penalty for the at least one policyholder based at least in part on the validation results.
 28. The method of claim 19, further comprising preventing by the business logic computer the insurance company and the service provider from exchanging their respective customer lists.
 29. An automated validation system for validating information used to determine insurance policy adjustments, comprising: an application server configured to obtain from a database information about at least one policyholder who is responsible for at least one property covered under a property insurance policy offered by an insurance company, wherein a portion of the information indicates that at least one property of the at least one policyholder is receiving remote monitoring services from a service provider, communicate with a service provider server to validate whether the at least one property of the at least one policyholder is currently receiving remote monitoring services from the service provider without revealing an identity of the at least one policyholder to the service provider, and store in the database validation results; and a business logic computer configured to determine an insurance policy adjustment for the at least one policyholder based at least in part on the stored validation results.
 30. The system of claim 29, wherein the business logic computer is configured to determine the insurance policy adjustment given to the at least one policyholder based at least, in part on, a type and a scope of coverage of remote monitoring services the at least one property is receiving.
 31. The system of claim 29, wherein the application server is further configured to request from the service provider server a hashed list of customers of the service provider who are receiving remote monitoring services for their properties.
 32. The system of claim 31, wherein the validation results include at least a comparison between the hashed list of customers of the service provider and a hashed list of policyholders of the insurance company currently receiving at least one insurance benefit due to their usage of remote monitoring services for their properties. 